-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for OKE Infra and Service Log Collection #100
base: main
Are you sure you want to change the base?
Conversation
7b86cf2
to
a37c91b
Compare
# Compartment of Logging LogGroup is not known at the time of policy creation via stack | ||
# We assume that Logging Log Groups are only created in either OKE or ONM compartments | ||
service_discovery_stmt = var.create_service_discovery_policies ? distinct([ | ||
"Allow dynamic-group ${local.dynamic_group_name} to manage log-groups in ${local.onm_compartment_scope}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Validate the case/behaviour of Service Stack, when the underlying resource/corresponding log/logGroup deleted
"Allow dynamic-group ${local.dynamic_group_name} to manage log-groups in ${local.onm_compartment_scope}", | ||
"Allow dynamic-group ${local.dynamic_group_name} to manage log-groups in ${local.oke_compartment_scope}", | ||
|
||
"Allow dynamic-group ${local.dynamic_group_name} to read log-content in ${local.onm_compartment_scope}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lets put a where clause to restrict this policy to service connector resource if that is sufficient
No description provided.